System and method for allocation of organizational resources

ABSTRACT

System and methods for storing electronic data is provided, where the system comprises a storage manager component and a management module associated with the storage manager component. The management module is configured to receive information related to storage activities associated with one or more storage operation components within the storage operation system under the direction of the storage manager component. The management module is adapted to predict storage operation resource allocations based on the received information related to the storage activities.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.11/639,830, filed Dec. 15, 2006, entitled SYSTEM AND METHOD FORALLOCATION OF ORGANIZATIONAL RESOURCES, which claims the benefit of U.S.Provisional Application Nos. 60/752,196, filed Dec. 19, 2005, and60/752,197, filed Dec. 19, 2005, each of which is incorporated herein byreference in its entirety. U.S. patent application Ser. No. 11/639,830is a continuation-in-part of U.S. application Ser. No. 11/120,619, filedMay 2, 2005, entitled HIERARCHICAL SYSTEMS AND METHODS FOR PROVIDING AUNIFIED VIEW OF STORAGE INFORMATION, which claims the benefit of U.S.Provisional Application No. 60/567,178, filed Apr. 30, 2004, each ofwhich is incorporated herein by reference in its entirety.

BACKGROUND

The invention disclosed herein relates generally to performing storageoperations on electronic data in a computer network. More particularly,the present invention relates to managing the allocation of resources ina storage operation system.

Current storage management systems employ a number of different methodsto perform storage operations on electronic data. For example, data canbe stored in primary storage as a primary copy or in secondary storageas various types of secondary copies including, as a backup copy, asnapshot copy, a hierarchical storage management copy (“HSM”), as anarchive copy, and as other types of copies.

A primary, copy of data is generally a production copy or other “live”version of the data which is used by a software application and isgenerally in the native format of that application. Primary copy datamay be maintained in a local memory or other high-speed storage devicethat allows for relatively fast data access if necessary. Such primarycopy data is typically intended for short term retention (e.g., severalhours or days) before some or all of the data is stored as one or moresecondary copies, for example to prevent loss of data in the event aproblem occurred with the data stored in primary storage.

Secondary copies include point-in-time data and are typically intendedfor long-term retention (e.g., weeks, months or years depending onretention criteria, for example as specified in a storage policy asfurther described herein) before some or all of the data is moved toother storage or discarded. Secondary copies may be indexed so users canbrowse and restore the data at another point in time. After certainprimary copy data is backed up, a pointer or other location indicia suchas a stub may be placed in the primary copy to indicate the currentlocation of that data.

Based on the many storage operations that may be performed on primary,secondary, or other types of storage data, information associated withthese storage operations may exists. For example, administrative usersor managers of a storage operation system may wish to leverage suchstorage operation information to a better understanding of systemoperation.

SUMMARY

System and methods for storing electronic data are provided, wherein, inone embodiment, the system comprises a storage manager component and amanagement module associated with the storage manager component. Themanagement module is configured to receive information related tostorage activities associated with one or more storage operationcomponents within the storage operation system under the direction ofthe storage manager component. The management module is adapted topredict storage operation resource allocations based on the receivedinformation related to the storage activities.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention is illustrated in the figures of the accompanying drawingswhich are meant to be exemplary and not limiting, in which likereferences are intended to refer to like or corresponding parts, and inwhich:

FIG. 1 is a block diagram of a storage operation cell in a system toperform storage operations on electronic data in a computer networkaccording to an embodiment of the invention;

FIG. 2 is a block diagram of a hierarchically organized group of storageoperation cells in a system to perform storage operations on electronicdata in a computer network according to an embodiment of the invention;

FIG. 3A is a block diagram of a hierarchically organized group ofstorage operation cells in a system to perform storage operations onelectronic data in a computer network according to an embodiment of theinvention;

FIG. 3B is a flow diagram of a method of utilizing storage operationinformation in one or more storage operation cells according to anembodiment of the invention;

FIG. 4A is an illustrative interface screen for entering reportgeneration scheduling information for trending and resource forecastingin accordance with one embodiment of the invention;

FIG. 4B is an illustrative interface screen for providing reportedresults based on the entered scheduling information shown in FIG. 4Aaccording to an embodiment of the invention;

FIG. 5A is another illustrative interface screen for entering reportgeneration scheduling information for trending and resource forecastingin accordance with another embodiment of the invention;

FIG. 5B is yet another illustrative interface screen for providingreported results based on the entered scheduling information shown inFig SA according to an embodiment of the invention;

FIG. 6A is an illustrative interface screen for entering reportgeneration scheduling information for providing data protection trendsaccording to an embodiment of the invention;

FIG. 6B is an illustrative interface screen for providing reportedresults based on the entered scheduling information shown in FIG. 6Aaccording to an embodiment of the invention;

FIG. 7 is a flow diagram of a method of utilizing reported failureinformation in one or more storage operation cells according to anembodiment of the invention;

FIG. 8A is an illustrative interface screen for entering reportgeneration scheduling information for evaluating failed storageoperation trends according to an embodiment of the invention;

FIG. 8B is an illustrative interface screen for providing reportedresults based on the entered scheduling information shown in FIG. 8Aaccording to an embodiment of the invention; and

FIGS. 9A-9D are illustrative interface screens for creating clientgroups within a storage operation system according to an embodiment ofthe invention.

DETAILED DESCRIPTION

FIG. 1 presents a block diagram of a storage operation cell in a systemto perform storage operations on electronic data in a computer networkaccording to an embodiment of the invention. As shown, the storageoperation cell includes a storage management component, such as storagemanager 100 and one or more of the following: a client 85, a data store90, a data agent 95, a media management component, such as a media agent125, a media management component index cache 130, a storage device 135,a storage management component index cache 105, a jobs agent 110, aninterface module 115, and a management agent 120. The system andelements thereof are exemplary of a modular storage management systemsuch as that further described in application Ser. No. 09/610,738,whichis incorporated herein by reference in its entirety. A storage operationcell may generally include combinations of hardware and softwarecomponents directed to performing storage operations on electronic data.Exemplary storage operation cells according to embodiments of theinvention include CommCells as embodied in the QNet storage managementsystem and the QiNetix storage management system by CommVault Systems ofOceanport, New Jersey, and as further described in application Ser. No.60/482,305 and application Ser. No. 09/354,058 which are herebyincorporated by reference in their entirety.

Storage operations cells may be related to backup cells and may provideall of the functionality of backup cells as further described inapplication Ser. No. 09/354,058. Storage operation cells may alsoperform additional types of storage operations and provided by othertypes of storage management functionality. Storage operation cellsperforming storage operations may also include, but are not limited to,creation, storage, retrieval, migration, deletion, and tracking ofprimary or production volume data, secondary volume data, primarycopies, secondary copies, auxiliary copies, snapshot copies, backupcopies, incremental copies, differential copies, Hierarchical StorageManagement (“HSM”) copies, archive copies, Information LifecycleManagement (“ILM”) copies, and other types of copies and versions ofelectronic data. Storage operation cells may also include an integratedmanagement console for providing users or system processes to interfacewith, in order to perform storage operations on electronic data.

A storage operation cell may be organized and associated with otherstorage operation cells by forming a logical hierarchy among variouscomponents of a storage management system. Storage operation cellsgenerally include a storage manager 100, and, one or more othercomponents including, but not limited to, a client computer 85, a dataagent 95, a media management component 125, a storage device 135, suchas a single instance storage device, and other components.

For example, a storage operation cell may contain a data agent 95 whichmay generally be-a software module that is responsible for performingstorage operations related to client computer 85 data that may be storedin data store 90 or another memory location. For example, data agent 95may provide archiving, migrating, and recovery of client computer data.A data agent may perform storage operations in accordance with one ormore storage policies or other preferences. A storage policy isgenerally a data structure or other information which includes a set ofpreferences and other storage criteria for performing a storageoperation. The preferences and storage criteria may include, but are notlimited to, a storage location, relationships between system components,network pathway to utilize, retention policies, data characteristics,compression or encryption requirements, preferred system components toutilize in a storage operation, and other criteria relating to a storageoperation. Storage policies may be stored to a storage manager index105, to archive media as metadata for use in restore operations or otherstorage operations, or to other locations or components of the system.

Each client computer 85 generally has at least one data agent 95 and thesystem may support many client computers 85. The system may alsogenerally provide a plurality of data agents 95 each of which may intendto perform storage operations related to data associated with adifferent application, for example, in order to backup, migrate, andrecover application specific data. For example, different individualdata agents 95 may be designed to handle MICROSOFT EXCHANGE data, LOTUSNOTES data, MICROSOFT WINDOWS 2000 file system data, MICROSOFT ACTIVEDIRECTORY OBJECTS data, and other types of data known in the art.

If a client computer 85 includes two or more ,types of data, one dataagent 95 may generally be required for each data type in order toperform storage operations related to client computer 85 data. Forexample, to backup, migrate, and restore all of the data on a MICROSOFTEXCHANGE 2000 server, the client computer 85 would use one MICROSOFTEXCHANGE 2000 mailbox data agent 95 to backup the EXCHANGE 2000mailboxes, one MICROSOFT EXCHANGE 2000 database data agent 95 to backupthe Exchange 2000 databases, one MICROSOFT EXCHANGE 2000 public folderdata agent 95 to backup the EXCHANGE 2000 public folders, and oneMICROSOFT WINDOWS 2000 file system data agent 95 to backup the clientcomputer's 85 file system. These data agents 95 may be treated as fourseparate data agents 95 by the system even though they reside on thesame client computer 85. Separate data agents may be combined to form avirtual data agent (not shown) for performing storage operations relatedto a specific application. Thus, the four separate data agents of theprevious example may be combined as a virtual data agent suitable forperforming storage operations related to all types of MICROSOFT EXCHANGE2000 and/or WINDOWS 2000 data.

The storage manager 100 may generally be a software module orapplication that coordinates and controls storage operations performedby the storage operation cell. The storage manager 100 may communicatewith all elements of the storage operation cell including clientcomputers 85, data agents 95, media management components 125, andstorage devices 135 regarding storage operations, for example, toinitiate and manage system backups, migrations, and recoveries. Thestorage manager 100 may also communicate with other storage operationcells.

The storage manager 100 may include a jobs agent 110 software modulewhich monitors the status of all storage operations that have beenperformed, that are being performed, or that are scheduled to beperformed by the storage operation cell. The jobs agent 110 may becommunicatively coupled with an interface agent 115 software module. Theinterface agent 115 may provide presentation logic, such as a graphicaluser interface (“GUI”), an application program interface (“API), orother interface by which users and system processes may be able toretrieve information about the status of storage operations and issueinstructions regarding the performance of storage operations. Forexample, a user may modify the schedule of a number of pending snapshotcopies or other types of copies. As another example, a user may use theGUI to view the status of all storage operations currently pending inall storage operation cells or the status of particular components in astorage operation cell.

Storage system management information may include, but is not limitedto, the status of various storage operations (past and present), storageoperation policies, storage operation scheduling, the configuration(e.g., associations) of components (e.g., media agents 125, storagedevices 135, clients 85, data agent 95, etc.) within the storageoperation system, the number of storage operation jobs carried out byeach of the storage operation system components, failure and loadbalancing information, network capacity information across variouscommunication links (e.g., links 117, 119), and other data managementrelated information. Such information may be stored in index 105, andassociated metabase, and/or any other storage devices associated withstorage manager 100.

A management interface module 122 within jobs agent component 110 mayfacilitate the accessing and processing of system information. Inaddition to allowing users of the storage operation system (e.g., systemadministrators) to monitor, control, and retrieve such information,management interface module 122 may generate reports indicative ofsystem operation which may include past, present or predictiveinformation relating to system performance. One or more users of astorage operation system may access a unified view of system managementinformation from management module 122 via interface module 115. Basedon this accessed information, various trending procedures and processmay be carried in order predict the growth requirements of the one ormore storage operation cells in a storage operation system. Aspreviously described, interface 115 may include a GUI, API, or othergraphical interface device capable of displaying, entering, and/orediting system management information to users such as storage systemadministrators.

As illustrated in FIG. 1, management interface module 122 may be amodule residing within jobs agent 110. Alternatively, managementinterface module 122 may be a separate module within storage manager100. Also, management interface module 122 may include a separate modulein communication with storage manager 100 via management agent 120. Forexample, management interface module 122 may receive storage managementrelated information from different modules with the storage operationcell, such as, data agents 95, media agents 125, storage devices 135,network traffic evaluation devices, and/or any other hardware devices,software modules, or combinations thereof, that may have or generateperformance related data or metrics based on storage operationactivities (e.g., copy operations, data migration, backups, etc.) withthe storage operation cells of a storage operation system.

The storage manager 100 may also include a management agent 120 softwaremodule. The management agent 120 may generally provide an interface withother management components 100 in other storage operations cellsthrough which information and instructions regarding storage operationsmay be conveyed. For example, a management agent 120 in a first storageoperation cell can communicate with a management agent 120 in a secondstorage operation cell regarding the status of storage operations in thesecond storage operation cell. A management agent 120 in a first storageoperation cell can communicate with a management agent 120 in a secondstorage operation cell to control the storage manager 100 (and othercomponents) of the second storage operation cell via management agent120 contained in the storage manager 100 of the second storage operationcell. The management agent 120 in the first storage operation cell maycommunicate directly with and control the components in the secondstorage management cell and bypasses the storage manager 100 in thesecond storage management cell. Storage operation cells can thus beorganized hierarchically among cells.

A media management component 125 may be a software module that conductsdata, as directed by a storage manager 100, between client computers 85and one or more storage devices 135. The media management component 125may communicatively be coupled with and generally configured to controlone or more storage devices 135. For example, the media managementcomponent 125 may instruct a storage device 135 to use a robotic arm orother means to load or eject a media cartridge, and to archive, migrate,or restore application specific data. The media management component 125may generally communicate with storage devices 135 via a local bus suchas a SCSI adaptor. In some embodiments, the storage device 135 may becommunicatively coupled to the media management component 125 via aStorage Area Network (“SAN”).

Each media management component 125 may maintain an index cache 130which stores index data the system generates during storage operationsas further described herein. For example, storage operations forMICROSOFT EXCHANGE data generate index data. Index data may include, forexample, information regarding the location of the stored data on aparticular media, information regarding the content of the data storedsuch as file names, sizes, creation dates, formats, application types,and other file-related criteria, information regarding one or moreclients associated with the data stored, information regarding one ormore storage policies, storage criteria, or storage preferencesassociated with the data stored, compression information,retention-related information, encryption-related information,stream-related information, and other types of information. Index datamay thus provides the system with an efficient mechanism for performingstorage operations including locating user files for recovery operationsand for managing and tracking stored data. The system generallymaintains two copies of the index data regarding particular stored data.A first copy may generally be stored with the data copied to a storagedevice 135. Thus, a tape may contain the stored data as well as indexinformation related to the stored data. In the event of a systemrestore, the index data stored with the stored data may be used torebuild a media management component index 130 or other index useful inperforming storage operations. In addition, the media managementcomponent 125 that controls the storage operation may also write anadditional copy of the index data to its index cache 130. The data inthe media management component index cache 130 may be generally storedon faster media, such as magnetic media, and is thus readily availableto the system for use in storage operations and other activities withouthaving to be first retrieved from the storage device 135.

Storage manager 100 may also maintains an index cache 105. Storagemanager index data may be used to indicate, track, and associate logicalrelationships and associations between components of the system, userpreferences, management tasks, and other useful data. For example, thestorage manager 100 may use its index cache 105 to track logicalassociations between media management components 125 and storage devices135. The storage manager 100 may also use its index cache 105 to trackthe status of storage operations to be performed, storage patternsassociated with the system components such as media use, storage growth,network bandwidth, Service Level Agreement (“SLA”) compliance levels,data protection levels, storage policy information, storage criteriaassociated with user preferences, retention criteria, storage operationpreferences, and other storage-related information. Index caches 105 and130 may typically reside on their corresponding storage component's harddisk or other fixed storage device.

For example, the jobs agent 110 of a storage manager component 100 mayretrieve storage manager index 105 data regarding a storage policy andstorage operation to be performed or scheduled for a particular client85. Jobs agent 110, either directly or via the interface module 115, maycommunicate with the data agent 95 at the client 85 regarding thestorage operation. In some embodiments, the jobs agent 110 may alsoretrieve from the index cache 105 a storage policy associated with theclient 85 and uses information from the storage policy to communicate tothe data agent 95 one or more media management components 125 associatedwith performing storage operations for that particular client 85 as wellas other information regarding the storage operation to be performed,such as retention criteria, encryption criteria, streaming criteria,etc. The data agent 95 may then package or otherwise manipulate theclient data stored in the client data store 90 in accordance with thestorage policy information and/or according to a user preference, andcommunicates this client data to the appropriate media managementcomponent(s} 125 for processing. Media management component(s) 125 maystore the data according to storage preferences associated with thestorage policy including storing the generated index data with thestored data, as well as storing a copy of the generated index data inthe media management component index cache 130.

In some embodiments, components of the system may reside and execute onthe same computer. In some embodiments, a client computer 85 componentsuch as a data agent 95, a media management component 125, or a storagemanager 100 may coordinate and direct storage operations as furtherdescribed in application Ser. No. 09/610,738. This client computer 85component can function independently or together with other similarclient computer 85 components.

FIG. 2 presents a block diagram of a hierarchically organized group ofstorage operation cells in a system to perform storage operations onelectronic data in a computer network according to an embodiment of theinvention. As shown, the system may include a master storage managercomponent 140, a first storage operation cell 145, a second storageoperation cell 150, a third storage operation cell 155, a fourth storageoperation cell 160, a fifth storage operation cell 165, and an nthstorage operation cell 170.

As previously described, storage operation cells may often becommunicatively coupled and hierarchically organized. For example, asshown in FIG. 2, master storage manager 140 may be associated with,communicates with, and directs storage operations for a first storageoperation cell 145, a second storage operation cell 150, a third storageoperation cell 155, a fourth storage operation cell 160, a fifth storageoperation cell 165, and an nth storage operation cell 170. In someembodiments, master storage manager 140 may not be part of anyparticular storage operation cell. In other embodiments (not shown),master storage manager 140 may itself be part of a storage operationcell.

Thus, master storage manager 140 may communicate with the managementagent of the storage manager of the first storage operation cell 145 (ordirectly with the other components of the first cell 145) regardingstorage operations performed in the first storage operation cell 145.For example, in some embodiments, the master storage manager 140 mayinstruct the first storage operation cell 145 how and when to performstorage operations, including the type of operation to perform, and thedata on which to perform the operation.

In other embodiments, master storage manager 140 may track the status ofits associated storage operation cells, such as the status of jobs,system components, system resources, and other items, by communicatingwith manager agents (or other components) in the respective storageoperation cells. In other embodiments, master storage manager 140 maytrack the status of its associated storage operation cells by receivingperiodic status updates from the manager agents (or other components) inthe respective cells regarding jobs, system components, systemresources, and other items. For example, in some embodiments, masterstorage manager 140 may use methods to monitor network resources such asmapping network pathways and topologies to, among other things,physically monitor storage operations and suggest alternate routes forstoring data as further described herein. The master storage manager 140may also use methods to monitor primary and secondary storage trends,storage status, media usage, data protection levels, and otherstorage-related information as further described herein.

In some embodiments, master storage manager 140 may store statusinformation and other information regarding its associated storageoperation cells and the system in an index cache or other data structureaccessible to the master storage manager 140. In some embodiments, asfurther described herein, the presentation interface of the masterstorage manager 140 accesses this information to present users andsystem processes with information regarding the status of storageoperations, storage operation cells, system components, and otherinformation of the system.

Storage operation cells may thus be organized hierarchically. Thus,storage operation cells may inherit properties from their parents or becontrolled by other storage operation cells in the hierarchy. Thus, insome embodiments as shown in FIG. 2, the second storage operation cell150 controls or is otherwise superior to the third storage operationcell 155, the fourth storage operation cell 160, the fifth storageoperation cell 165, and the nth storage operation cell 170. Similarly,the fourth storage operation cell 160 controls the fifth storageoperation cell 165, and the nth storage operation cell 170.

Storage operation cells may also be organized hierarchically accordingto criteria such as function, geography, architectural considerations,or other factors useful in performing storage operations. For example,in one embodiment storage operation cells may be organized according totypes of storage operations: the first storage operation cell 145 may bedirected to performing snapshot copies of primary copy data, and thesecond storage operation cell 150 is directed to performing backupcopies of primary copy data or other data. For example, in anotherembodiment, the first storage operation cell 145 may represent ageographic segment of an enterprise, such as a Chicago office, and asecond storage operation cell 150 represents a different geographicsegment, such as a New York office. In this example, the second storageoperation cell 150, the third storage operation cell 155, the fourthstorage operation cell 160, the fifth storage operation cell 165, andthe nth storage operation cell 170 may represent departments within theNew York office. Alternatively, these storage operation cells may befurther divided by function performing various types of copies for theNew York office or load balancing storage operations for the New Yorkoffice.

In some embodiments, hierarchical organization of storage operationcells facilitates, among other things, system security and otherconsiderations. For example, in some embodiments, only authorized usersmay be allowed to access or control certain storage operation cells. Forexample, a network administrator for an enterprise might have access toall storage operation cells including the master storage manager 140.However, a network administrator for only the New York office, accordingto a previous example, may only satisfy access criteria for gainingaccess to the second storage operation cell 150, the third storageoperation cell 155, the fourth storage operation cell 160, the fifthstorage operation cell 165, and the nth storage operation cell 170 whichmay comprise the New York office storage management system.

In some embodiments, hierarchical organization of storage operationcells facilitates storage management planning and decision-making. Forexample, in some embodiments, a user of the master storage manager 140may view the status of all jobs in the associated storage operationcells of the system as well as the status of each component in everystorage operation cell of the system. The user can may then plan andmake decisions based on this global data. For example, the user may viewhigh-level reports of summary information regarding storage operationsfor the entire system, such as job completion status, componentavailability status, resource usage status (such as network pathways,etc.), and other information. The user may also drill down through menusor use other means to obtain more detailed information regarding aparticular storage operation cell or group of storage operation cells.

In other embodiments, master storage manager 140 may alert the user whena particular resource is unavailable or congested. A storage device maybe at or near capacity or require additional storage media.Alternatively, a storage manager in a particular storage operation cellmay be unavailable due to hardware failure, software problems, or otherreasons. In some embodiments, master storage manager 140 (or anotherstorage manager within the hierarchy of storage operation cells) mayutilize the global data regarding its associated storage operation cellsat its disposal to suggest solutions to such problems prior tooccurrence. For example, the master storage manager 140 may alert theuser that a storage device in a particular storage operation cell wasfull or otherwise congested, and then suggest, based on job and datastorage information contained in its index cache, an alternate storagedevice.

Master storage manager 140 (or other network storage manager) maycontain programming directed to analyzing the storage patterns andresources of its associated storage operation cells and which suggestsoptimal or alternate methods of performing storage operations. Thus, forexample, master storage manager 140 may analyze traffic patterns inorder to determine that snapshot data should be sent via a differentnetwork segment or to a different storage operation cell or storagedevice. In some embodiments, users may direct specific queries to masterstorage manager 140 regarding predicting storage operations or regardingstorage operation information.

FIG. 3 is a block diagram of a hierarchically organized group of storageoperation cells in a system to perform storage operations on electronicdata in a computer network according to an embodiment of the invention.As shown, FIG. 3 may include a first storage operation cell 175, asecond storage operation cell 180, a third storage operation cell 185, aclient 190 in communication with a primary volume 195 storing productionor other “live” data, a storage manager component 200 in communicationwith a storage manager index data store 205, a media managementcomponent 210 in communication with a media management component index215, a secondary storage device or volume 220, and a master storagemanager component 225 in communication with a master storage managerindex data store 230.

According to an embodiment of the invention, the first storage operationcell 175 may be directed to a particular type storage operation, such asSRM storage operations. For example, the first storage operation cell175 may monitor and perform SRM-related calculations and operationsassociated with primary volume 195 data. Thus, the first storageoperation cell 175 may include a client component 190 in communicationwith a primary volume 195 storing data. For example, client 190 may bedirected to using EXCHANGE data, SQL data, ORACLE data, or other typesof production data used in business applications or other applicationsand stored in primary volume 195. Storage manager component 200 in cell175 may contain SRM modules or other logic directed to monitoring orotherwise interacting with attributes, characteristics, metrics; andother information associated with the data stored in primary volume 195.Storage manager 200 may track and store this information and otherinformation in storage manager index 205. For example, in someembodiments, storage manager component 200 may track the amount ofavailable space and other similar characteristics of data associatedwith primary volume 195. In some embodiments, as further describedherein, storage manager component 200 may also issue alerts or takeother actions when the information associated with primary volume 195satisfies certain criteria, such as alert criteria (e.g., breach ofstorage capacity threshold levels).

In addition to storing alert criteria and storage data characteristics,storage manager 200 in cell 175 may also track and save (e.g., withinindex 205) other system management information. For example, informationassociated with various aspects of storage operation activities withincell 175 may be accessed by storage manager 200 and stored in index 205.

For example, the information associated with storage activities mayinclude, but is not limited to, a logged time stamp for each performedstorage operation; storage capacity used during each storage operation;status of storage operation (e.g., partial or full failure); pathwaystaken over one or more communication links (e.g., link 240) betweenclient 190 and primary storage 195 during each storage operation;aggregate storage capacity available within storage device 195, numberof clients 190 within storage cell 175; number of storage devices (e.g.,storage 195 and index 205) within storage operation cell 175; andnetwork congestion information associated with each pathway over which astorage operation is performed. Storage manager 200 may periodicallysend such stored system management information to a master storagemanager such as storage manager 225 in storage operation cell 175.Alternatively, master storage manager 225 may poll storage manager 200of cell 175 and/or other storage manager components (e.g., storagemanager 200 of storage operation cell 180) in order to access systemmanagement information.

The storage manager 200 in storage operation cell 175 may include amanagement interface module such as management interface 122 shown inFIG. 1. If so, the management interface may access the system managementinformation from index 205 for processing. Once processed, variousforecasting information associated with the storage resources in storagecell 175 may be determined and sent to master storage manager 225. Forexample, based on previous storage capacity trends and available storagecapacity associated with storage device 195, the management interface(not shown) may predict a need for added storage capacity within threeweeks.

Thus, in the provided example, the predicted storage needs may provide ameasure of growth rate associated with a storage resource such asprimary storage 195, which may provide system administrators andmanagers with an opportunity to allocate new and/or alternativeresources prior to a point in time when the resource may no longer beavailable. In another example, information related to traffic on a datapathway may be monitored in order to develop a trend in failureconditions versus data traffic on a specific pathway at different times.Thus, based on this information, the management interface module may,for example, users with the opportunity to select additional oralternative data pathways at times when data transmissions over aparticular pathway previously lead to a failure in storage operations.In some embodiments, the storage manager may automatically assign theappropriate resources according to the processing of the systemmanagement information by its respective management interface module(e.g., in the case were data loss or system failure is imminent or topart of an ongoing optimization process, etc).

The second storage operation cell 180 may be directed to another typestorage operation, such as HSM storage operations. For example, secondstorage operation cell 180 may perform backups, migrations, snapshots,or other types of HSM-related operations known in the art. For example,in some embodiments, data may be migrated from faster and more expensivestorage such as magnetic storage to less expensive storage such as tapestorage.

In some embodiments, storage operation cells may also contain logicalgroupings of the same physical devices. Thus, the second storageoperation cell 180 may include client component 190 in communicationwith primary volume 195 for storing data, and client component 190 andprimary volume 195 in the second storage operation cell 180 may be thesame physical devices as the client component 190 and primary volume 195in the first storage operation cell 175. Similarly, in some embodiments,storage manager component 200 and index 205 in the second storageoperation cell 180 may be the same physical devices as the storagemanager component and index in the first storage operation cell 175.Storage manager component 200 may, however, also contain HSM modules orother logic associated with second storage operation cell 180 that maybe directed to performing HSM storage operations on primary volume 195data.

The second storage operation cell 180, therefore, may also contain amedia management component 210, a media management component index 215,and a secondary storage volume 220 directed to performing HSM-relatedoperations on primary copy data. For example, storage manager 200 maymigrate primary copy data from primary volume 195 to secondary volume220 using media management component 210. Storage manager 200 may alsotrack and store information associated with primary copy migration andother similar HSM-related operations in storage manager index 205. Forexample, in some embodiments, storage manager component 200 may directHSM storage operations on primary copy data according to a storagepolicy associated with primary copy 195 and stored in index 205. In someembodiments, storage manager 200 may also track where primary copyinformation is stored, for example, in secondary storage 220.

Storage manager 200 in cell 180 may also track and save (e.g., withinindex 205) system management information associated with various aspectsof storage operation activities. For example, the information associatedwith storage activities may include, but is not limited to, a loggedtime stamp for each performed storage operations; storage capacity usedduring each storage operation; status of storage operations (e.g.,partial or full failure); pathways taken over one or more communicationlinks (e.g., link 240) between client 190, media agent 210, andsecondary storage 220 during each storage operation; pathways taken overone or more communication links (e.g., links 245 and 250) between client190 and primary storage 195 during each storage operation; aggregatestorage capacity available within storage device 195; number of clients190 within storage cell 180; number of storage devices (e.g., storagedevices 195, 220, and 205) within storage operation cell 180; number ofmedia agents 210 within storage cell 180; and network congestioninformation associated with each pathway over which a storage operationis performed. Storage manager 200 may periodically send such storedsystem management information to a master storage manager such asstorage manager 225 in storage operation cell 180. Alternatively, masterstorage manager 225 may poll storage manager 200 of cell 180 and/orother storage manager components (e.g., storage manager 200 of storageoperation cell 175) in order to access such system managementinformation.

The storage manager 200 in storage operation cell 180 may also include amanagement interface module such as management interface 122 shown inFIG. 1. The management interface that may include reporting and analysissoftware component that may search for and retrieve certain systemmanagement information from portions of the system including, forexample, index 205 or an associated metabase (not shown) indicative ofsystem performance. The reporting software may analyze this informationto generate certain reports that may reveal trends in system operationsuch as the use of certain system resources over time, observed andprojected system growth, resource utilization rate, failure andcongestion rates, performance information for specific groups ofresources, etc. This allows system users to identify, track and predictperformance and operational trends within the system providingoperational visibility, allowing users to manage system configurationand resources effectively.

For example, based on information regarding previous storage capacityusage and available storage capacity of one or more secondary storagedevices 220, the reporting and analysis software component may analyzeand forecast a need for added storage capacity within a certain periodof time (e.g., two months). Thus, the predicted storage needs may beindicative of growth rate associated with a particular storage resourcesuch as storage device 220, which may provide system administrators withan opportunity to allocate additional and/or alternative resources suchas additional storage media prior to a point in time when the resourceis no longer viable.

In another example, information associated with the number of storageoperations performed and the number of active media agents 210coordinating those storage operations in certain cells 180 may beretrieved and analyzed by the reporting software. The results of such ananalysis may provide a system administrator with information regardingresource usage including emerging patterns and trends providing anopportunity to identify bottlenecks or stress points and configure,assign or allocate additional media agents to cope with changingconditions. For example, if certain media agents are operating at ornear full capacity, additional ones may be added. In this example, ifcertain other media agents are operating significantly below fullcapacity, storage operations from over burdened media agents may movedto these media agents to load balance. In some embodiments, the systemmay automatically perform these tasks without user input (e.g., in anemergency situation when failure or data loss are imminent, or as partof an ongoing process to optimize system performance or enhanceefficiency, etc.).

The third storage operation cell 185 may contain a master storagemanager 225 and a master storage manager index 230. In some embodiments(not shown), additional storage operation cells may be hierarchicallylocated between the third storage operation cell 185 and the firststorage operation cell 175 or the second storage operation cell 180. Insome embodiments, additional storage operation cells hierarchicallysuperior to the third storage operation cell 185 may also be present inthe hierarchy of storage operation cells.

In some embodiments, the third storage operation cell 185 may also bedirected to performing a type of storage operation, such as integrationof SRM and HSM data from other storage operation cells, such as firststorage operation cell 175 and second storage operation cell 180. Inother embodiments, the third storage operation cell 185 may also performother types of storage operations and may also be directed to HSM, SRM,or other types of storage operations. In some embodiments, the masterstorage manager 225 of the third storage operation cell 185 mayaggregate and process network and storage-related data provided by othermanager components 200 in other storage operation cells 175 and 180 inorder to provide, among other information, reporting informationregarding particular cells, groups of cell, or the system as a whole.

For example, master storage manager 225 in storage operation cell 185may also include a management interface module such as managementinterface 122 shown in FIG. 1 which may include a reporting and analysiscomponent. This management interface (not shown) may access managementinformation received from both storage manager 200 in cell 175 andstorage manager 200 in storage cell 180. Master storage manager 225 may,therefore, provide system administrators with a unified view of allstorage operation cells within a configured storage operation system.

Although each storage operation cell may process system managementinformation via a respective management interface module (e.g.,generating performance metrics, trending, forecasting, and resourceallocation), processing of system management information may be providedcentrally at master storage manager 225. In such embodiments, systemmanagement information may be sent by the storage manager of eachstorage operation cell (e.g., storage manager 200 of cell 175) to masterstorage manager 225 following each storage operation. Alternatively,master storage manager 225 may periodically poll storage certainoperation cells for system management information based on the report oranalysis to be performed.

FIG. 3B is a flow diagram 400 generally illustrating some steps involvedin using storage operation information (e.g., system managementinformation) to generate certain reports or metrics according to anembodiment of the invention. At step 402, information associated withvarious storage operations within a storage operation cell may betracked and stored by the storage manager, media agent or other mediamanagement component associated with one or more storage operationcells. For example, certain system management information such asinformation regarding the data or information copied (e.g., data size,type, packaging or other format details, security, location,destination, size, etc.), the time and date associated with past,present or future the storage operation, the policy responsible forinitiating the storage operation, the pathway used Ito be used completethe storage operation, the components involved to be involved in thestorage operation, and the status of the storage operation etc.

In some embodiments, this information may present in an index, database,metabase or other information storage device associated with one or moremaster storage managers or other media management components associatedwith one or more storage operation cells. Thus, in operation, acomputing device (not shown) performing the calculations associated witha report may request and collect information from various master storagemanagers regarding certain information relating to metrics to becalculated (described further herein) (step 404). Once collected, thisinformation may be processed to generate a specified report or obtainthe desired performance metric(s). This may include providingforecasting and trending analyses as further described herein that maybe used for identifying stress points within the system which may beused to assist in resource allocation (dynamic, automatic or manual) inone or more other storage operation cells (e.g., cells 175 and 180)associated with the master storage operation cell (step 408) .

In other embodiments, information regarding system performance may becollected from various media management components within storageoperation cells and reported to an associated master storage managerwhich may fulfill request as described above or be reported directly tothe computing device requesting such information. In such embodiments,the computing device may consult with a master storage manager to locatemedia management components that have information of interest. Thecomputing device may thus consult multiple storage operation cells insearch of relevant information, collate and/or arrange the relevantinformation for subsequent processing to generate requested reports ormetrics.

At step 404, it may be determined whether certain information is storedin or available in one or more master storage managers (e.g., masterstorage manager 225 shown in FIG. 3A). If so, the information may beretrieved and processed accordingly. This may involve initially pollingor otherwise communicating with master storage managers within thesystem (or specified subset with in the system) to identify storageoperation cells with information relevant to calculating desiredmetrics. A list of such cells may be created and used as a startingpoint in collecting relevant metric information. If however, it isdetermined that the information is not present in one or more masterstorage manager(s), the information may be retrieved from one or moremedia management components in a similar manner (step 406). A computingdevice including metric calculation software and an optional userinterface may generate reports and provide forecasting and resourceallocation operation based on the accessed information received fromthese storage manager components (step 408) . Such reports may bepresented to a user for consideration or may be analyzed by systemmanagement software monitoring system performance.

FIG. 4A shows an illustrative interface screen 412 that may be generatedby reporting and analysis software for performing certain calculationsbased on system performance information according to an embodiment ofthe invention. For example, screen 412 may be generated by managementinterface module 122 (FIG. 1), and presented to users via interfacemodule 115 (FIG. 1). As shown, the left side of screen 412 may include adirectory tree 414 or other menu structure that allows users to accessand manage different parts of a storage operation system from a unifieddisplay. For example, directory tree 414 may include a “reports” field416, which may, among other things, provide users with the ability torequest and monitor report results associated with various aspects ofthe storage operation system.

Selecting a report from field 416 may cause the system to generateprovide a user display 420 allowing a user to specify parameters andgenerate certain reports regarding a particular category or occurrenceof interest. Such reports may be preprogrammed by a vendor and/orcreated by an end user through reports generation tool (not shown) usingtechniques and procedures known in the art.

As shown, such reports may include, but are not limited to Billing, DataProtection, Data Recovery, Primary Storage or Commcell Growth and mayinclude multiple subcategories as shown in connection with DataProtection reports on the left hand side of screen 412. However, it willbe understood that these reports are only illustrative and that anyother reports relating to system operation or performance may be addedif desired. By selecting, for example, “CommCell Growth” element 418from reports field 416, display 420 may be presented to the user. Insome embodiments, users may enter certain specifics as filter parametersthat provide or generate criteria that specifying data or occurrences ofinterest. For example, display 420 may include menu option 422 forselecting components or modules of the storage operation system that maybe used in generating certain reports associated with the selectedcomponents or modules. For example, as illustrated in the embodiment ofFIG. 4A, subclient(s) 424 has been selected.

Display 420 may include various time range selection options 426. Forexample, a user may select a report that provides information based on acertain frequency (e.g., a weekly basis) and/or over a specified timerange (e.g., over last 8 weeks). Thus, frequency option 428 and rangeoption 430 may specify a report generated based on subclient relatedinformation collected on a weekly basis (i.e., based on option 428) overa specified eight-week period (i.e., based on option 430). In otherembodiments, a range of dates may be specified if desired.

Using an output or result field 431, a user may specify that a certainformat for displaying results that may include various graphicaldisplays for displaying report results. In the provided example, a bargraph display is selected, however any suitable layout may selected ofdesired (e.g., pie chart, a line plot across and x-y axis, etc.). Areport may be generated for subclients of a particular storage operationcell or other selected storage operation cells using selection field432. Thus, as shown in exemplary screen 412, specific storage operationcells 436 and 438 may be selected and included in a subsequentlygenerated report. After specifying the information certain information,By clicking on “Generate” button 440 in screen 412, a Commcell growthreport may be generated, as by clicking on “Generate” button 440 inscreen 412 (shown in FIG. 4B).

FIG. 4B shows an illustrative report screen 445 for provides resultsbased on the information specified in FIG. 4A according to an embodimentof the invention. The display option for the report may be changed usingchart option menu 447. For example, the current report display forsubclient components associated with the storage operation cell “Hummer”(i.e., as indicated by information bar 452 within screen 445) isdisplayed by bar graph 450. Bar graph 450 may display the number ofsubclients in use during storage operations, as indicated at 455, as afunction of a selected time range, indicated at 457. Bar 460 mayindicate that during the week of Monday, September 12 (i.e., #09/12#),twenty-eight subclients were involved in storage operations. Similarly,bar 462 may indicate that during the week of Monday, September 19 (i.e.,#09/19#), twenty-four subclients were involved in storage operations,which indicates a reduction compared to the previous week. Graph 450also illustrates that over an eight-week period (i.e., from Mon.08/01-Mon. 09/19), six weeks show no subclient activity, as indicated at465.

In addition to graph 450, table 470 may also illustrate the resultsassociated with subclient activities in storage operation cell Hummer.The generated results may provide user and administrators with anindication as to how a particular component or module has been utilized.This may include the amount of data traffic, data copied or moved to andfrom various locations, resources used such as certain media managementcomponents or storage device capacity, system bandwidth etc.

Based on this information, operational trends may be determined, whichmay provide the ability to forecasting future resource needs. Forexample, the results shown in graph 450 or table 470 may indicate thatthere is no increase associated with the number of active subclientswithin the storage operation cell (e.g., based on entries 460 and 462).Thus, no additional resources may need to be allocated based on theobserved information, which, in some instances, may indicate the storageoperation cell may additional resources to spare. However, if theresults had shown an increase in the number of subclients used in thestorage operation cell, this increased trend over the eight-week timeperiod allows the system or a user to recognize and plan for anyresource shortage or bottleneck including adding or assigningalternative resources to the storage operation cell such as mediaagents, data paths, storage devices such as tape drives and associatedstorage media (e.g., tapes, discs, etc.) .

In determining a trend or trends in the growth results, variousalgorithms, formula, and/or data manipulation techniques such as linearregression, extrapolation, interpolation, best fit curves, likelihoodfunctions or other techniques known in the art may be employed based onthe data points available and the desired metrics to be calculated.

FIG. 5A shows another illustrative display 512 generated by a reportingmodule according to an embodiment of the invention. Similar to theinterface screen of FIG. 4A, screen 512 may also include directory tree514, which may allow users to access and manage different parts of astorage operation system from a unified display. For example, directorytree 514 may also include a “reports” field 516. As shown, screen 512may include menu option 522 for selecting components or modules of thestorage operation system that may be used in generating growth reportsassociated with the selected components or modules. In the illustratedembodiment, Media Agent(s) option 524 has been selected.

Scheduling options 526 may include various time range selection options.For example, a user may select a growth report that provides informationbased on frequency (e.g., a weekly basis) and over a specified timerange (e.g., over last 8 weeks). Thus, frequency option 528 and datarange option 530 may provide a report that may be generated based ondata agent related information that is collected once a week (i.e.,based on option 528) over an eight-week period (i.e., based on option530). Scheduling option 531 may include a display chart option fordisplaying the report results. In the provided example, a bar graphdisplay may be selected. A report may be generated for data agent of aparticular one or more selected storage operation cells using selectionfield 532. Thus, based on exemplary screen 512, storage operation cells536 and 538 may be selected for growth report generation purposes. Byclicking on “Generate” button 540 in screen 512, a corresponding reportmay be generated, as illustrated in FIG. 5B.

FIG. 5B shows an illustrative interface screen 545 for providingreported results based on the entered scheduling information shown inFIG. 5A according to an embodiment of the invention. The display optionfor the growth report may be changed using chart option menu 547. Forexample, the current growth report display for data agent componentsassociated with the storage operation cell Hummer” (i.e. , as indicatedby information bar 552 within screen 545) is displayed by bar graph 550.Bar graph 550 may display the number of data agents in use duringstorage operations, indicated at 555, as a function of a selected timerange, indicated at 557. Bar 560 may indicate that during the week ofMonday, September 12 (i.e., #09/12#), eight data agents were involved instorage operations.

Similarly, bar 562 may indicate that during the week of Monday,September 19 (i.e., #09/19#), eight subclients were also involved instorage operations, which indicates no change in the number of dataagents compared to the previous week. Graph 550 also illustrates thatover an eight-week period (i.e., from Mon. 08/01 Mon. 09/19), six weeksshow no data agent activity, as indicated at 565.

In addition to graph 550, table 570 also illustrates the resultsassociated with the number of active data agents in storage operationcell Hummer in table form. The generated results may provide users andadministrators with an indication as to how a particular component ormodule has been utilized. As previously described, based on thisinformation trends may be determined, which provides the ability toforecast future resource needs. For example, the results shown in graph550 or table 570 may indicate that there is no increase associated withthe number of active data agents used within the storage operation cell.However, if the results indicate an increase in the number of dataagents used in the storage operation cell, this increased trend over theeight-week time period may have provided an opportunity for evaluatingand adding more data agent resources to the storage operation cell. Thenumber of data agent resources forecasted for addition to a storageoperation cell may be based on other calculated metrics associated withthe storage operation components such as, for example, the utilizedbandwidth of data pathways during storage operations, status of storageoperations, data load, available storage devices etc. As mentionedabove, various other algorithms, formulae, and/or data manipulationtechniques may be incorporated based on the metrics used to evaluateresources within the one or more storage operation cells within astorage operation system.

FIG. 6A is yet another illustrative screen 612 generated by a managementinterface module for entering scheduling information for trending andresource forecasting according to an embodiment of the invention. Forexample, screen 612 may also be generated by a reports interface module122 (FIG. 1), and accessed and displayed to users via interface module115 (FIG. 1). The left side of screen 612 may include a directory tree614 that allows users to access and manage different parts of a storageoperation system from a unified display. For example, directory tree 614may include a “reports” field 616, which may, among other things,provide system administrators or authorized uses with the ability tomonitor and manage reports associated with various aspects of thestorage operation system. By selecting, for example, “CommCell Growth”element 418 from “reports” field 616, an illustrative display 620 may bepresented to an administrative user. Display 620 may include menu option622 for selecting components or modules of the storage operation systemthat may be used in generating growth reports associated with theselected components or modules. For example, in the illustratedembodiment of FIG. 6A, Data Protection Job(s) 624 has been selected.

Scheduling options 626 may include various time range selection options.For example, a user may select a growth report that provides informationbased on frequency (e.g., a daily basis) and over a specified time range(e.g., over last 7 days). Thus, frequency option 628 and range option630 may provide a growth report that may be generated based on thenumber of data protection jobs carried out daily (i.e., based on option628), and over a seven day period (i.e., based on option 630).

Scheduling option 631 may include a display chart option for displayingthe growth report results. In the provided example, a bar graph displayis selected. A growth report may be generated for performed dataprotection jobs of a particular one or more selected storage operationcells, whereby the storage operation cells are selected using selectionfield 632. Thus, based on exemplary screen 612, storage operation cells636 and 638 may be selected for growth report generation purposes. Byclicking on “Generate” button 640 in screen 612, a corresponding growthreport may be generated, as illustrated in FIG. 6B.

FIG. 6B shows an illustrative interface screen 645 for providingreported results based on the entered scheduling information shown inFIG. 6A according to an embodiment of the invention. The display optionfor the growth report may be changed using chart option menu 647. Forexample, the current report display for data protection jobs associatedwith the storage operation cell Hummer (i.e., as indicated byinformation bar 652 within screen 645) is displayed by bar graph 650.Bar graph 650 may display the number of data protection jobs, indicatedat 655, as a function of a selected time range, as indicated at 657. Bar660 may indicate that during the weekend of September 16-18 (i.e.,#09/16-09/18#), forty data protection jobs were performed. Similarly,bar 662 may indicate that on the following Monday, September 19 (i.e.,#09/19#), eighteen data protection jobs were performed, indicating areduction in data protection jobs compared to the weekend. Graph 650also illustrates that over the period of about a week (i.e., from Tues.09/13-Mon. 09/19), for three days, no data protection jobs areperformed, as indicated at 665.

In addition to graph 650, table 670 may also illustrate the growthresults associated with the listed data protection jobs in storageoperation cell Hummer. The generated results may provide users andadministrators with information regarding various data protectionactivities that may have been performed. Based on this information,trends may be determined, which may provide opportunities forforecasting future resource needs. For example, the results shown ingraph 650 or table 670 may indicate that there may be a trend associatedwith the increased number of data protection jobs occurring overweekends. Using this information, additional storage system resourcesmay be assigned to handle the increased data load associated withperforming the increased number of data protection jobs during busyperiods such the weekends. For example, additional storage devicesand/or media agents may be utilized during these periods.

In determining a trend or trends in the growth results, variousalgorithms, formula, and/or data manipulation techniques may beincorporated based on the metrics used to evaluate resources within theone or more storage operation cells within a storage operation system.Moreover, system parameters may change or vary according to needs of theend-user of the storage operation system. For example, if the end-useris in the financial business, the metrics used for determining when andhow often to perform data protection jobs may differ from those used inother industries such as retail.

For example, the storage capacity thresholds used to trigger a warningcondition may differ depending on the usage rate of storage capacity.If, for example, the rate of data storage capacity usage is high, suchas in a financial application, it may be desired to use a lowerthreshold (e.g., 60%) for a warning condition, thus, providingsufficient advance notice to secure additional resources. In a retailapplication, however, the rate of consumption of storage media may bemuch lower, so that a warning threshold level may be set a higherpercentage (e.g., 80%) which still providing sufficient time to secureadditional resources. Thus the reporting modules of the presentinvention, may be used to analyze storage capacity usage information topredict future storage resource needs, (e.g., additional storagedevices) before the resources become overburdened, reach maximumcapacity, or become other unusable or inoperable.

In some embodiments of the invention, user-defined metrics may beutilized for generating system management information that may beassociated with one or more storage operation cells within a storagesystem. In such embodiments, users or system administrators may be ableto apply desired metrics for particular storage activities. For example,different statistical predictive analysis routines may be applied todata storage activities (e.g., read and/or write operation) associatedwith storage devices. Other examples may include applying metricsassociated with the data pathways taken by storage data duringparticular storage operations involving sensitive data (e.g., classifiedinformation).

In other embodiments of the invention, default-metrics may be utilizedfor generating system management information that may be associated withone or more storage operation cells within a storage system. In suchembodiments, based on end-user requirements, the storage manager andmanagement interface module may provide a set of standard metrics (e.g.,storage device priority level) and scheduling criteria (e.g., databackup frequency) for processing storage activity information prior togenerating reports (e.g., growth reports). For example, if the storagesystem is used in retail based industries, a different set of defaultsettings may be used than if the storage system is being utilized forstorage management in, for example, law enforcement. For example, in lawenforcement applications, data protection jobs may be scheduled to occurmore often, the threshold values for storage capacity alerts associatewith storage devices may be lower, and growth reports associated withthe data protection jobs may be generated more often (see FIG. 6B).

FIG. 8A is an illustrative interface screen 712 that may be used forspecifying and evaluating failed storage operations according to anembodiment of the invention. For example, similar to the screensdescribed above, screen 712 may be generated by management interfacemodule 122 (FIG. 1), and accessed and displayed to users via interfacemodule 115 (FIG. 1). The left side of screen 712 may include directorytree 714, which allows users to access and manage different parts of astorage operation system from a unified display. By selecting, forexample, “CommCell Growth” element 718 from reports field 716, anillustrative display of various management scheduling options may bepresented to a user via display 720. Display 720 may include varioustime range selection options. For example, a user may select to receivejob failure reports over a specified time range (e.g., over last 7days). Thus, option 725 may be used to access failure reports over thelast seven days. Scheduling option 730 may include a failure occurrencesetting 732, which may allow users to specify the number of consecutivejob failures that are to be captured and considered a single failure.This allows a user to exclude spurious or accidental failures and definea number of consecutive failures considered to be operationallyrelevant.

For example, in storage systems where the end-user requirements arerelatively fault tolerant, the number of consecutive job failures thatmay be defined as a single failure occurrence may be set to higher value(e.g., five consecutive failures defined as one occurrence) as opposedto more sensitive applications (e.g., two failures). Scheduling option730 may also include a display setting 734, which provides an indicationof the number of fault occurrence details that may be displayed in thefailure report.

As illustrated in the exemplary embodiment of FIG. 8A, the displayedoccurrences are set to five, but other numbers may be used if desired. Afailure report may be generated for a particular one or more selectedstorage operation cells, whereby storage operation cells or storageoperation cell groups may be selected using selection fields 744 and746, respectively.

FIG. 8B shows an illustrative interface screen 745 for providingreported results based on the entered scheduling information shown inFIG. 8A according to an embodiment of the invention. Table 770 mayillustrate consecutive failures occurrences for the selected “East CoastCommCells” client group, as indicated at information bar 772. Thegenerated results may provide users and administrators with informationregarding the occurrences of failures with the selected storageoperation cell group (i.e., specified by “East Cost CommCells”). Forexample, within storage operation cell 776, storage operation cellapplication “Windows 2003 32-bit File System” 778 has incurred failuresduring default backup operations. The failure reports may be displayedas failure occurrences, as indicated by 780, whereby for each failureoccurrence, time and date information 782 may be displayed.

Based on this information, trends may be determined, which may provideinformation associated with the root cause of certain failures. Forexample, a failure occurrence may be correlated with other storageoperation metrics and other storage related parameters to determine thepossible cause of the failure. If, for example, metrics indicatesufficient storage capacity, transmission bandwidth, and mediamanagement components, but one or more links in the data pathway to astorage device show increased congestion or failures, such congestionmay be attributed to the possible fault. Such information may becorrelated with other reports and performance information to identifycommon resources involved for fault isolation.

Using trending or forecasting analysis, other fault occurrences may beevaluated and compared with each other in a similar manner. If, forexample, other fault occurrences show that a particular pathway orstorage device has an increasing number of faults, this may indicate adevice or pathway is close to failure or overburdened. This allows thesystem or a user to employ additional or alternative resources tocorrect a detected problem or inefficiency. For example, the one or moredata pathways may be re-routed or additional data communications linkmay be installed to alleviate any detected problem.

FIGS. 9A-9D are illustrative interface screens for creating clientgroups within a storage operation system according to an embodiment ofthe invention. Referring to FIG. 9A, a new group of storage operationcells may be created by, for example, clicking on Cell-Client Groupfield 902 and selecting the New Cell-Client Group field 904 fromdirectory tree 906. By selecting New Cell Client Group field 904, aninterface screen, such as exemplary interface screen 915 illustrated inFIG. 9B, may be presented to system users according to an embodiment ofthe invention. Using screen 915, a system administrator or authorizeduser may assign a name for the creation of a new storage operation cellgroup by making an entry in field 917.

Description information associated with the cell group may be entered infield 920. Similarly time-zone selection may be set using pull-down menu922. Once the fields in Screen 915 have been entered, an exemplaryillustrative interface screen, such as screen 925 shown in FIG. 9C, maybe presented according to an embodiment of the invention. From screen925, one or more storage operation components may be selected. Forexample, utilizing fields 930, one or more storage operation cells(e.g., draco-61 galaxy, dimsum 5.0) may be selected for incorporation inthe created storage operation cell group. Also, for example, fields 935may be used to select one or more client computers (e.g., DAGGERCOMMVAULT.COM) for each of the selected storage operation cellsindicated in fields 930. Once the one or more storage operationcomponents have been selected, the illustrative interface screen 940 ofFIG. 9D may be used to select one or more applications for use inassociation with the selected storage operation cell group. Asillustrated in FIG. 9D, fields 945 may provide a selectable list ofapplications associate with the storage operation cells associated withthe created group. Also, as indicated at fields 950, a list ofapplications may also be selected for the other storage systemcomponents (e.g., data agents) within the group's storage operationcells. Once the selections have been made from fields 945 and 950,“Finish” button 955 may be activated.

Systems and modules described herein may comprise software, firmware,hardware, or any combination(s) of software, firmware, or hardwaresuitable for the purposes described herein. Software and other modulesmay reside on servers, workstations, personal computers, computerizedtablets, PDAS, and other devices suitable for the purposes describedherein. Software and other modules may be accessible via local memory,via a network, via a browser or other application in an ASP context, orvia other means suitable for the purposes described herein. Datastructures described herein may comprise computer files, variables,programming arrays, programming structures, or any electronicinformation storage schemes or methods, or any combinations thereof,suitable for the purposes described herein. User interface elementsdescribed herein may comprise elements from graphical user interfaces,command line interfaces, and other interfaces suitable for the purposesdescribed herein. Screenshots presented and described herein can bedisplayed differently as known in the art to input, access, change,manipulate, modify, alter, and work with information.

While the invention has been described and illustrated in connectionwith preferred embodiments, many variations and modifications as will beevident to those skilled in this art may be made without departing fromthe spirit and scope of the invention, and the invention is thus not tobe limited to the precise details of methodology or construction setforth above as such variations and modification are intended to beincluded within the scope of the invention.

What is claimed is: 1.-20. (canceled)
 21. A method of identifyingstorage system resources to be added to a storage system, wherein themethod is performed by a computing system having a processor and memory,the method comprising: managing one or more secondary copy storageoperations between a plurality of client computing devices and one ormore secondary storage devices using a plurality of data agents residingon the plurality of client computing devices and a plurality of mediamanagement components associated with the one or more secondary storagedevices, said managing secondary copy storage operations furthercomprising: packaging data on the plurality of client computing deviceswith the plurality of data agents, wherein each data agent is configuredto package data of a predefined data type, receiving the packaged dataat the plurality of media management components, the plurality of mediamanagement components configured to process the packaged data fordifferent types of the one or more secondary storage devices, andcreating one or more secondary copies of the packaged data on the one ormore secondary storage devices; receiving information relating to atleast a trend of a number of active data agents; forecasting a need fordata storage capacity in the storage system based at least on the trendof the number of active data agents; and identifying one or more storagesystem resources to be added to the storage system based on theforecasting.
 22. The method of claim 1, wherein different mediamanagement components are configured to process the packaged data fordifferent types of the one or more secondary storage devices, wherein atleast one media management component processes the packaged data for atape drive and at least one media management component processes thepackaged data for a disk drive.
 23. The method of claim 21, wherein:receiving the packaged data further comprises receiving informationrelating to at least a trend of a number of data protection jobs; andforecasting the need for data storage capacity in the storage system isfurther based at least on the trend of the number of data protectionjobs.
 24. The method of claim 21, wherein: receiving the packaged datafurther comprises receiving information relating to at least a trend ofa number of active clients and sub-clients; and forecasting the need fordata storage capacity in the storage system is further based at least onthe trend of the number of active clients and sub-clients.
 25. Themethod of claim 21, wherein: receiving the packaged data furthercomprises receiving information relating to at least a trend of a numberof active media agents; and forecasting the need for data storagecapacity in the storage system based at least on the trend of the numberof active media agents.
 26. The method of claim 21, wherein: receivingthe packaged data further comprises receiving information relating to atleast a trend of a number of fault occurrences; and forecasting the needfor data storage capacity in the storage system is further based atleast on the trend of the number of fault occurrences.
 27. The method ofclaim 21, further comprising activating a warning upon determining thatthe number of active data agents has reached a threshold number.
 28. Astorage operation system for use in a data storage network, the storageoperation system comprising: a storage manager component executing inone or more processors on a computing device and configured to manageone or more secondary copy operations between a plurality of clientcomputing devices and one or more storage devices using a plurality ofdata agents residing on the plurality of client computing devices and aplurality of media management components, wherein one or more dataagents from the plurality of data agents are configured to package datalocated on a data store associated with a client computing device asdirected by the storage manager component prior to a secondary copystorage operation of the data, wherein each data agent is configured topackage data of a predefined data type, and the plurality of mediamanagement components are configured to receive and process the packageddata from the one or more data agents for different types of the one ormore secondary storage devices; and a reporting component associatedwith the storage manager component, the reporting component configuredto: receive information relating to at least a trend of a number ofactive data agents, forecast a need for data storage capacity in thestorage system based at least on the trend of the number of active dataagents, and identify one or more storage system resources to be added tothe storage system based on the forecasting.
 29. The system of claim 28,wherein different media management components are configured to processthe packaged data for different types of the one or more storagedevices, wherein at least one media management component processes thepackaged data for a tape drive and at least one media managementcomponent processes the packaged data for a disk drive such that the oneor more storage devices contain a backup copy of the data located on thedata store.
 30. The system of claim 28, wherein the storage systemresources comprise at least one of clients, sub-clients, media agents,storage devices, data agents, storage media, and data transfer paths.31. The system of claim 28, wherein the reporting component furtherreceives information relating to at least a trend of a number of dataprotection jobs and forecasts the need for data storage capacity in thestorage system based at least on the trend of the number of dataprotection jobs.
 32. The system of claim 28, wherein the reportingcomponent further receives information relating to at least a trend of anumber of active clients and sub-clients and forecasts the need for datastorage capacity in the storage system based at least on the trend ofthe number of active clients and sub-clients.
 33. The system of claim28, wherein the reporting component further receives informationrelating to at least a trend of a number of active media agents andforecasts the need for data storage capacity in the storage system basedat least on the trend of the number of active media agents.
 34. Thesystem of claim 28, wherein the reporting component further receivesinformation relating to at least a trend of a number of faultoccurrences and forecasts the need for data storage capacity in thestorage system based at least on the trend of the number of faultoccurrences.
 35. The system of claim 28, wherein the reporting componentactivates a warning upon determining that the number of active dataagents has reached a threshold number.
 36. A computer-readable,non-transitory storage medium having one or more computer-executablemodules, the one or more computer-executable modules comprising: astorage manager module configured to manage one or more secondary copystorage operations between a plurality of client computing devices andone or more secondary storage devices using a plurality of data agentsresiding on the plurality of client computing devices and a plurality ofmedia management components, wherein one or more data agents from theplurality of data agents are configured to package data located on adata store associated with a client computing device as directed by thestorage manager component prior to a secondary copy storage operation ofthe data, wherein each data agent is configured to package data of apredefined data type, and the plurality of media management componentsare configured to receive and process the packaged data from the one ormore data agents for different types of the one or more secondarystorage devices; and a reporting module associated with the storagemanager component, the reporting component configured to: receiveinformation relating to at least a trend of a number of active dataagents; forecast a need for one or more storage system resources in thestorage system based at least on the trend of the number of active dataagents; and identify one or more storage system resources to be added tothe storage system based on the forecasting.
 37. The computer-readable,non-transitory storage medium of claim 36, wherein different mediamanagement components are configured to process the packaged data fordifferent types of the one or more storage devices such that the one ormore storage devices contain a backup copy of the data located on thedata store.
 38. The computer-readable, non-transitory storage medium ofclaim 36, wherein at least one media management component is configuredto process the packaged data for a tape drive and at least one mediamanagement component is configured to process the packaged data for adisk drive.
 39. The computer-readable, non-transitory storage medium ofclaim 36, wherein the storage system resources comprise at least one ofclients, sub-clients, media agents, storage devices, data agents,storage media, and data transfer paths.
 40. The computer-readable,non-transitory storage medium of claim 36, wherein the reporting modulefurther receives information relating to at least a trend of a number ofdata protection jobs, and forecasts the need for data storage capacityin the storage system based at least on the trend of the number of dataprotection jobs.
 41. The computer-readable, non-transitory storagemedium of claim 36, wherein the reporting module further receivesinformation relating to at least a trend of a number of active clientsand sub-clients and forecasts the need for data storage capacity in thestorage system based at least on the trend of the number of activeclients and sub-clients.
 42. The computer-readable, non-transitorystorage medium of claim 36, wherein the reporting module furtherreceives information relating to at least a trend of a number of activemedia agents and forecasts the need for data storage capacity in thestorage system based at least on the trend of the number of active mediaagents.